Storage device and operating method thereof

ABSTRACT

A storage device includes a nonvolatile memory device and a controller. The nonvolatile memory device includes a plurality of memory blocks, each of which includes string selection transistors connected to a plurality of string selection lines, ground selection transistors connected to a plurality of ground selection lines, and memory cells connected to a plurality of word lines. The controller reads valid data groups of a first memory block and writes the read valid data groups in a second memory block, during a read reclaim operation. The controller assigns locations of the second memory block, at which the valid data groups are written, based on read counts of the valid data groups.

CROSS-REFERENCE TO RELATED APPLICATIONS

This U.S. non-provisional patent application claims priority under 35 U.S.C. §119 to Korean Patent Application No. 10-2016-0111905, filed on Aug. 31, 2016 in the Korean Intellectual Property Office, the entire contents of which are hereby incorporated by reference.

BACKGROUND 1. Technical Field

The present disclosure relates to a semiconductor circuit. More particularly, the present disclosure relates to a storage device and an operating method thereof.

2. Background Information

A storage device refers to a device which stores data under control of a host device such as a computer, a smartphone, and a smart pad. The storage device includes a device which stores data on a magnetic disk, such as a hard disk drive (HDD), or a device which stores data on a semiconductor memory (in particular, a nonvolatile memory), such as a solid state drive (SSD) or a memory card.

The nonvolatile memory includes a read only memory (ROM), a programmable ROM (PROM), an electrically programmable ROM (EPROM), an electrically erasable and programmable ROM (EEPROM), a flash memory device, a phase-change RAM (PRAM), a magnetic RAM (MRAM), a resistive RAM (RRAM), a ferroelectric RAM (FRAM), etc.

The volume of storage devices has increased as semiconductor manufacturing technologies develop. Additionally, the degree of integration of storage devices continues to increase as semiconductor manufacturing technologies develop. The high degree of integration of the storage devices makes it possible to reduce costs needed to manufacture the storage device. However, the high degree of integration of the storage devices causes scale-down and structure change of the storage devices. Thus, various new problems occur with the high degree of integration. Since such issues cause a damage of data stored in the storage device, the reliability of the storage device may decrease. There is a need for a method and a device capable of improving the reliability of the storage device.

SUMMARY

Embodiments of the present disclosure provide a storage device with improved reliability and an operating method thereof.

According to an embodiment, a storage device includes a nonvolatile memory device and a controller. The nonvolatile memory device includes a plurality of memory blocks, each of which has string selection transistors connected to a plurality of string selection lines, ground selection transistors connected to a plurality of ground selection lines, and memory cells connected to a plurality of word lines. During a read reclaim operation, the controller reads valid data groups of a first memory block and writes the read valid data groups in a second memory block. The controller assigns locations of the second memory block, at which the valid data groups are written, based on read counts of the valid data groups.

According to another embodiment, an operating method of a storage device, which includes a nonvolatile memory device and a controller, includes counting the number of read operations of data groups written in a first memory block of the nonvolatile memory device, and copying the data groups written in the first memory block to a second memory block of the nonvolatile memory device during a read reclaim operation. Locations of the data groups are assigned based on the read counts of the data groups during the read reclaim operation.

According to another embodiment, a storage device includes a nonvolatile memory device and a controller. The nonvolatile memory device has a first memory block and a second memory block. The controller: (1) attributes an amount of accumulated read disturbances to each of multiple valid-data groups stored within the first memory block, (2) identifies a first valid-data group, among the valid-data groups, having an amount of accumulated read disturbances exceeding a predetermined value, (3) identifies a second valid-data group, among the valid-data groups, having an amount of accumulated read disturbances that does not exceed the predetermined value, (4) writes, during a read reclaim operation and in response to identifying the first valid-data group, the first valid-data group to a first memory location within the second memory block that has a first degree of susceptibility to a read disturbance, and (5) writes, during the read reclaim operation and in response to identifying the second valid-data group, the second valid-data group to a second memory location within the second memory block that has a second degree of susceptibility to the read disturbance. The second degree of susceptibility to the read disturbance is greater than the first degree of susceptibility to the read disturbance.

BRIEF DESCRIPTION OF THE FIGURES

The above and other objects and features will become apparent from the following description with reference to the following figures, wherein like reference numerals refer to like parts throughout the various figures unless otherwise specified, and wherein:

FIG. 1 is a block diagram illustrating a storage device according to an embodiment of the present disclosure;

FIG. 2 is a flowchart illustrating an operating method of a storage device according to an embodiment of the present disclosure;

FIG. 3 illustrates an example of a memory block according to an embodiment of the present disclosure;

FIG. 4 illustrates an example of a structure of a cell string in a memory block of FIG. 3;

FIG. 5 illustrates an example in which read weights are set, according to an embodiment of the present disclosure;

FIG. 6 illustrates an example of threshold voltages of memory cells and data bits corresponding thereto;

FIG. 7 illustrates an example in which read weights are assigned according to distances between the substrate SUB and selected memory cells and a location of target data of pieces of data written in the selected memory cells;

FIG. 8 illustrates an example of read weights assigned in consideration of string selection lines of a memory block;

FIG. 9 is a flowchart illustrating an example in which a read weight is adjusted according to the number of times that a read operation is performed;

FIG. 10 is a flowchart illustrating an example in which a read weight is adjusted based further on a temperature associated with a read operation;

FIG. 11 is a block diagram illustrating a controller according to an embodiment of the present disclosure;

FIG. 12 is a block diagram illustrating a storage device, according to another embodiment of the present disclosure;

FIG. 13 is a flowchart illustrating an operating method of the storage device, according to another embodiment of the present disclosure;

FIG. 14 shows an example in which the degrees of read disturbance differ from each other for respective locations of memory cells;

FIG. 15 shows an example in which data groups of a selected memory block are written in a new memory block during a read reclaim operation;

FIG. 16 shows an example in which a controller performs a read reclaim operation;

FIG. 17 shows another example in which the controller performs a read reclaim operation;

FIG. 18 shows an example in which data groups are set, according to an embodiment of the present disclosure; and

FIG. 19 is a block diagram illustrating a controller, according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

Below, embodiments of the present disclosure will be described more fully with reference to accompanying drawings such that an ordinary one in the art may implement embodiments described herein.

FIG. 1 is a block diagram illustrating a storage device 100 according to an embodiment of the present disclosure. Referring to FIG. 1, the storage device 100 includes a nonvolatile memory device 110, a controller 120, and a buffer memory 130.

The nonvolatile memory device 110 may perform a write operation, a read operation, and an erase operation under control of the controller 120. The nonvolatile memory device 110 may receive a write command, an address, and data from the controller 120, and may write the data in a location of a storage space specified by or otherwise determinable from the address. The nonvolatile memory device 110 may receive a read command and an address from the controller 120, may read data from a location of a storage space specified by or otherwise determinable from the address, and may output the read data to the controller 120. The nonvolatile memory device 110 may receive an erase command and an address from the controller 120 and may erase data of at a location of a storage space specified by or otherwise determinable from the address.

The nonvolatile memory device 110 may include multiple memory blocks BLK1 to BLKz. Each of the memory blocks BLK1 to BLKz may include multiple memory cells. The memory cells may form a storage space of the nonvolatile memory device 110. Each of the memory blocks BLK1 to BLKz may further include selection transistors that make it possible to select memory cells independently of each other. The memory blocks BLK1 to BLKz may be distinguished according to an operational characteristic or a structural characteristic of the nonvolatile memory device 110. An example in which the memory blocks BLK1 to BLKz are distinguished from each other will be described with reference to FIG. 3.

The nonvolatile memory device 110 may include a flash memory, a phase change random access memory (PRAM), a ferroelectric RAM (FeRAM), a magnetic RAM (MRAM), a resistive RAM (RRAM), etc.

The controller 120 may access the nonvolatile memory device 110 and the buffer memory 130. The controller 120 may perform a write operation, a read operation, and an erase operation in response to a request of an external host device (not illustrated). The controller 120 may write write-requested data in the nonvolatile memory device 110, and may read and output read-requested data from the nonvolatile memory device 110.

The controller 120 may manage the storage device 100 by using the buffer memory 130. For example, the controller 120 may temporarily store data to be written in the nonvolatile memory device 110 or data read from the nonvolatile memory device 110 in the buffer memory 130. The controller 120 may load metadata, which is needed to manage the nonvolatile memory device 110, on the buffer memory 130.

The controller 120 may receive a request which is based on logical addresses, from the external host device. A flash translation layer FTL that is driven by the controller 120 may translate a logical address to a physical address of the nonvolatile memory device 110. The controller 120 may provide the physical address to the nonvolatile memory device 110. Mapping data MD that is needed for translation between a logical address and a physical address may be stored in the nonvolatile memory device 110 and may be loaded and used on the buffer memory 130. The flash translation layer FTL may perform translation between a logical address and a physical address based on the mapping data MD loaded on the buffer memory 130.

The controller 120 may count read operations performed in the nonvolatile memory device 110. For example, the controller 120 may manage a read count with regard to each memory block or each erase unit of the nonvolatile memory device 110. The erase unit may be a part of each memory block or a combination of two or more memory blocks and may indicate a set of memory cells that are simultaneously erased in an erase operation. Below, for descriptive convenience, a description associated with each memory block may be regarded as being associated with each memory block or each erase unit.

With regard to a read count, the controller 120 may include a weight module WM and a counter CNT. The weight module WM may detect or calculate a read weight based on a read target of the nonvolatile memory device 110 identified by or otherwise corresponding to a physical address or a location of the read target. When a read operation is performed on each memory block and a read weight is detected or calculated, the counter CNT may increase the read count by the read weight. For example, the counter CNT may add the read weight to the read count when data is written in each memory block. The read weight may be selected from two or more values based on a read target selected in each memory block or a location of the read target. The controller 120 may determine whether to perform a refresh operation of each memory block, based on the read count.

In an embodiment, each of the flash translation layer FTL, the weight module WM, and the counter CNT of the controller 120 may be implemented with a circuit, a state machine, software, firmware, or a combination of two or more thereof.

FIG. 2 is a flowchart illustrating an operating method of the storage device 100 according to an embodiment of the present disclosure. Referring to FIGS. 1 and 2, in operation S110, the controller 120 may receive a read command and an address from an external host device. The controller 120 may receive, for example, a read request including a logical address from the external host device.

In operation S120, the controller 120 may select a read operation. For example, the flash translation layer FTL may translate a logical address to a physical address of the nonvolatile memory device 110 based on the mapping data MD. The controller 120 may provide a read command and the physical address to the nonvolatile memory device 110. In response to the read command, the nonvolatile memory device 110 may read data from memory cells corresponding to the physical address, and may output the read data to the controller 120. The controller 120 may output the data received from the nonvolatile memory device 110 to the external host device. The data read from the nonvolatile memory device 110 may be buffered by the buffer memory 130 before output to the external host device.

In operation S130, the controller 130 may detect a read weight based on the physical address. For example, memory cells that are selected according to the physical address as a target of the read operation may be identified, and the weight module WM may detect a read weight corresponding to a location (e.g., a physical address) of the selected memory cells. For example, read weights corresponding to locations (e.g., addresses) of memory cells may be previously stored as nonvolatile information in the controller 120. Also, like the mapping data MD, the read weights may be previously stored in the nonvolatile memory device 110 and may be loaded and used on the buffer memory 130.

In operation S140, the controller 120 may increase the read count by the detected read weight. For example, the counter CNT may add the read weight detected by the weight module WM to a previous read count.

Operation S130 and operation S140 may be carried out in parallel with a read operation that is performed in operation S120.

In operation S150, the controller 120 may determine whether the read count reaches a threshold value. If the read count does not reach the threshold value (S150=No), the process ends. If the read count reaches the threshold value (S150=Yes), operation S160 is performed. In operation S160, the controller 120 may perform a refresh operation. For example, the controller 120 may schedule the refresh operation of a memory block identified by or otherwise corresponding to the physical address.

A read disturbance may occur whenever a read operation is performed on each memory block. The read disturbance may stress memory cells that are not selected as a read target. For example, the read disturbance may cause a change in threshold voltages of unselected memory cells. Data stored in unselected memory cells may vary according to accumulation of the read disturbance.

The refresh operation includes reading valid data from memory cells of a memory block and writing the read data in memory cells of another memory block. If the refresh operation is performed, data that is written in a memory block and experiences the read disturbances may be newly written in another memory block. The influence of the read disturbance disappears when data is newly written in another memory block. Accordingly, if the refresh operation is performed, the influence of the read disturbance disappears, and thus the reliability of data may be recovered.

The storage device 100 according to an embodiment of the present disclosure may recover the reliability of data through the refresh operation before data stored in each memory block is damaged due to accumulation of the read disturbance to such an extent that the damaged data is not recoverable.

The weight module WM according to an embodiment of the present disclosure detects a read weight based on a physical address of memory cells of each memory block on which a read operation is performed, that is, a physical location thereof. The read weight may be appreciated as a value that is obtained by quantifying the read disturbance occurring when the read operation is performed on each memory block.

The counter CNT according to an embodiment of the present disclosure may accumulate read weights detected for each memory block as a read count. The read count may be appreciated as a value that is obtained by quantifying the accumulated read disturbance(s) of each memory block.

The storage device 100 according to an embodiment of the present disclosure, as described with reference to FIG. 2, may perform the refresh operation based on a read count that is managed by the weight module WM and the counter CNT. That is, the influence of the read disturbance that varies according to a location of memory cells of each memory block selected as a read target may be used to determine whether to perform the refresh operation. As the refresh operation is performed, the reliability of data written in the nonvolatile memory device 110 may be corrected. Also, the number of times that the refresh operation is performed in the storage device 100 may decrease, and the speed of the storage device 100 may be improved.

FIG. 3 illustrates an example of a memory block BLKa according to an embodiment of the present disclosure. Referring to FIG. 3, multiple cell strings CS may be arranged on a substrate SUB in rows and columns. The cell strings CS may be connected in common to a common source line CSL that is formed on (or in) the substrate SUB. In FIG. 3, a location of the substrate SUB is exemplified to help understand a structure of the memory block BLKa. An embodiment is exemplified in FIG. 3 as the common source line CSL is connected to lower ends of the cell strings CS. However, it is enough to electrically connect the common source line CSL to the lower ends of the cell strings CS. However, embodiments of the present disclosure may not be limited to the case that the common source line CSL is physically located at the lower ends of the cell strings CS. In an embodiment, the cell strings CS are shown in FIG. 3 as being arranged 4 by 4. However, embodiments of the present disclosure are not limited to a 4 by 4 arrangement of cell strings CS.

Cell strings CS of each row may be connected to a corresponding one of first to fourth ground selection lines GSL1 to GSL4 and a corresponding one of first to fourth string selection lines SSL1 to SSL4. Cell strings CS of each column may be connected to a corresponding one of first to fourth bit lines BL1 to BL4. For ease of illustration, cell strings CS that are connected to the second and third ground selection lines GSL2 and GSL3 or the second and third string selection lines SSL2 and SSL3 are depicted to be blurry.

Each cell string CS may include at least one ground selection transistor GST connected to a corresponding ground selection line, multiple memory cells MC respectively connected to multiple word lines WL1 to WL8, and at least one (or two) string selection transistors SST connected to a corresponding string selection line SSL. In each cell string CS, the ground selection transistor GST, the memory cells MC, and the string selection transistor SST may be serially connected to each other along a direction perpendicular to the substrate SUB and may be sequentially stacked along a direction perpendicular to the substrate SUB.

Memory cells of the cell strings CS that are arranged at the same height (or order) from the substrate SUB or the ground selection transistor GST may be connected to the same word line. Memory cells of the cell strings CS that are arranged at different heights (or orders) from the substrate SUB or the ground selection transistor GST may be connected to different word lines.

The memory block BLKa may be provided at a three-dimensional (3D) memory array. The 3D memory array is monolithically formed in one or more physical levels of arrays of memory cells MC having an active area disposed above a silicon substrate and circuitry associated with the operation of the memory cells MC. The circuit associated with an operation of memory cells MC may be located above or within such substrate. The term “monolithic” means that layers of each level of the array are directly deposited on the layers of each underlying level of the 3D memory array.

In an embodiment of the present disclosure, the 3D memory array includes vertical cell strings CS (or NAND strings) that are vertically oriented such that at least one memory cell is located over another memory cell. Each memory cell may comprise a charge trap layer. Each cell string may further include at least one selection transistor SST placed over the memory cells MC. The at least one selection transistor may have the same structure as the memory cells MC and may be formed uniformly with the memory cells MC.

The following patent documents, which are hereby incorporated by reference, describe suitable configurations for three-dimensional memory arrays, in which the three-dimensional memory array is configured as multiple levels, with word lines and/or bit lines shared between levels: U.S. Pat. Nos. 7,679,133; 8,553,466; 8,654,587; 8,559,235; and US Pat. Pub. No. 2011/0233648.

FIG. 4 is a view illustrating an example of a structure of a cell string CS in the memory block BLKa of FIG. 3. Referring to FIGS. 3 and 4, a pillar PL is provided on the substrate SUB such that the pillar PL extends in a direction perpendicular to the substrate SUB to make contact with the substrate SUB. Each of the ground selection line GSL, the word lines WL1 to WL8, and the string selection lines SSL illustrated in FIG. 4 may be formed of a conductive material parallel with the substrate SUB, for example, a metallic material. The pillar PL may be in contact with the substrate SUB through the conductive materials forming the string selection lines SSL, the word lines WL1 to WL8, and the ground selection line GSL.

A sectional view taken along a line A-A′ is also illustrated in FIG. 4. In an embodiment, a sectional view of a first memory cell MC1 corresponding to a first word line WL1 is illustrated. The pillar PL may include a cylindrical body BD. An air gap AG may be defined in the interior of the body BD. The body BD may include P-type silicon and may be an area where a channel will be formed. The pillar PL may further include a cylindrical tunnel insulating layer TI surrounding the body BD and a cylindrical charge trap layer CT surrounding the tunnel insulating layer TI. A blocking insulating layer BI may be provided between the first word line WL and the pillar PL. The body BD, the tunnel insulating layer TI, the charge trap layer CT, the blocking insulating layer BI, and the first word line WL may constitute a charge trap type transistor that is formed in a direction perpendicular to the substrate SUB or to an upper surface of the substrate SUB. A string selection transistor SST, a ground selection transistor GST, and other memory cells may have the same structure as the first memory cell MC1.

In the process of manufacturing the cell string CS, a width of the pillar PL or a cross-sectional area of the pillar PL which is parallel to the upper surface of the substrate SUB may become smaller as a distance from the substrate SUB decreases. Accordingly, when the same voltage is applied to bodies of the ground selection transistor GST, the memory cells MC, and the string selection transistors SST, an electric field formed at a memory cell adjacent to the substrate SUB or at the ground selection transistor GST may be greater than an electric field formed at a memory cell distant from the substrate SUB or at the string selection transistor SST. Similarly, when the same voltage is applied to the ground selection line GSL, the word lines WL1 to WL8, and the string selection lines SSL, the electric field formed at a memory cell adjacent to the substrate SUB or at the ground selection transistor GST may be greater than an electric field formed at a memory cell distant from the substrate SUB or at the string selection transistor SST. The above-described characteristic may have an influence on the read disturbance that is generated while a read operation is performed.

In an embodiment, during a read operation, a selection read voltage is applied to a word line that is connected to memory cells selected as a read target. The selection read voltage has a level within a threshold voltage range of memory cells. Since the strength of an electric field at the selected memory cells is relatively small, the read disturbance may not occur at the selected memory cells or may occur very little. During the read operation, a non-selection read voltage is applied to each word line connected to memory cells that are not selected as the read target. The non-selection read voltage has a level exceeding the threshold voltage range of the memory cells. Since the strength of an electric field at unselected memory cells is relatively great, the read disturbance may occur at the unselected memory cells.

In particular, a level of the non-selection read voltage applied to unselected word lines immediately adjacent to the selected word line is higher than a level of the non-selection read voltage applied to other unselected word lines. Accordingly, the read disturbance that occurs at memory cells connected to unselected word lines adjacent to other unselected word lines may be greater than the read disturbance that occurs at memory cells connected to unselected word lines adjacent to the selected word lines. The read disturbance that occurs at memory cells connected to unselected word lines adjacent to each other may be referred to as “first read disturbance”.

Also, as described with reference to FIG. 4, the strength of an electric field at a memory cell becomes greater as a distance between the memory cell and the substrate SUB or the ground selection transistor GST decreases. Accordingly, the read disturbance occurring at a memory cell becomes greater as a distance between the memory cell and the substrate SUB or the ground selection transistor GST decreases. The read disturbance that occurs at memory cells connected to lower word lines close to the substrate SUB, for example, first to fourth word lines WL1 to WL4 may be referred to as “second read disturbance”.

When a read operation is performed on lower word lines (or word lines adjacent to or close to the substrate SUB, some (but not all) memory cells connected to the lower word lines may experience both the first read disturbance and the second read disturbance. A third read disturbance may occur due to the overlap between the first read disturbance and the second read disturbance. The third read disturbance may be the strongest read disturbance that occurs when a read operation is performed on the memory block BLKa.

As described with reference to FIGS. 1 and 2, refresh may be used to solve the read disturbance accumulated at memory cells. For example, in the memory block BLKa, the quantity of read disturbance that the memory cells may tolerate may be calculated, measured, or predicted. Also, the quantity of read disturbance occurring when each read operation is performed on a memory block may be calculated, measured, or predicted. The number of read operations that the memory block BLKa can tolerate, that is, a threshold value may be calculated based on the tolerable quantity of read disturbance and the quantity of read disturbance of each read operation.

If the quantity of read disturbance occurring when a read operation is performed once is set to be equal to or more than a value of the third read disturbance, the refresh operation may be performed before data written in the memory block BLKa is damaged. Accordingly, the reliability of data written in the memory block BLKa may be maintained. However, the number of read operations of the memory block BLKa that cause the refresh operation is inversely proportional to the number of times that the refresh operation is performed. An increase in the number of refresh operations causes a decrease in an operating speed of the storage device 100.

In contrast, if the quantity of read disturbance occurring when a read operation is performed once is set to be lower than a value of the third read disturbance, the number of times that the refresh operation is performed on the memory block BLKa may decrease. However, if the read operation of the memory block BLKa causing the read disturbance is iteratively performed (i.e., multiple times), data written in the memory block BLKa may be lost due to a high read disturbance (e.g., the third read disturbance level) before the refresh operation is performed.

The storage device 100 according to an embodiment of the present disclosure may detect a read weight based on an address indicating a location of memory cells or word lines selected as a target of a read operation, and may increase a read count based on the detected read weight. The read weight may be set in consideration of the quantity of practical read disturbance occurring during a read operation performed on each word line. Accordingly, it may be possible to prevent data written in the memory block BLKa from being lost due to the read disturbance and to reduce the number of times that a refresh operation is performed. That is, a storage device with improved speed and reliability is provided. Below, adjacent to the substrate SUB or a distance from the substrate SUB may be interpreted as meaning adjacent to the substrate SUB or the ground selection transistor GST or a distance from the substrate SUB or the ground selection transistor GST. Distance as the word is used herein, however, can be measured by the number (if any) of intervening transistors, as well as by more traditional measures such as in centimeters or inches even if the traditional measures are imprecise estimates of an actual distance from a substrate.

FIG. 5 illustrates an example in which read weights are set, according to an embodiment of the present disclosure. Referring to FIGS. 3, 4, and 5, the first read disturbance and the second read disturbance may overlap more (i.e., occur more frequently) as memory cells selected as a read target become closer to the substrate SUB. The first read disturbance and the second read disturbance may overlap less (i.e., occur less frequently) as memory cells selected as a read target become more distant from the substrate SUB. As the first read disturbance and the second read disturbance overlap more, the high level of the third read disturbance that actually occurs due to a single read operation performed on the memory block BLKa increases. As the first read disturbance and the second read disturbance overlap less, the high level of the third read disturbance that actually occurs due to a single read operation performed on the memory block BLKa decreases.

The word lines WL1 to WL8 of the memory block BLKa may be classified into first, second, third, and fourth word line groups WLG1, WLG2, WLG3, and WLG4 based on the above-described characteristics. For example, the word lines WL1 to WL8 may be grouped according to distances from the substrate SUB. A first read weight W_1 may be assigned to the first and second word lines WL1 and WL2 of which the distance from the substrate SUB is the shortest. A read count may increase by the first read weight W_1 when a read operation is performed on memory cells connected to one of the first and second word lines WL1 and WL2.

Based on distances from the substrate SUB, a second read weight W_2 may be assigned to the second word line group WLG2 including third and fourth word lines WL3 and WL4. A third read weight W_3 may be assigned to the third word line group WLG3 including fifth and sixth word lines WL5 and WL6. A fourth read weight W_4 may be assigned to the fourth word line group WLG4 including seventh and eighth word lines WL7 and WL8. As a distance from the substrate SUB increases, a read weight of memory cells, in other words, a read weight associated with a word line group (or a word line) corresponding to (or connected to) memory cells may decrease. For example, the second read weight W_2 may be smaller than the first read weight W_1, the third read weight W_3 may be smaller than the second read weight W_2, and the fourth read weight W_4 may be smaller than the third read weight W_3.

As described above, if a read weight is adjusted according to a distance between memory cells selected as a read target and the substrate SUB, the storage device 100 may be provided with improved speed and reliability. In particular, if a read weight decreases as a distance between the substrate SUB and the selected memory cells increases, the storage device 100 with improved speed and reliability is provided.

FIG. 6 illustrates an example of threshold voltages of memory cells MC and data bits corresponding thereto. In FIG. 6, the abscissa (X-axis value) represents a threshold voltage Vth of a memory cell MC, and the ordinate (Y-axis value) represents the number of memory cells MC. In an embodiment, an example in which three bits are written in each memory cell MC is illustrated in FIG. 6.

Referring to FIGS. 3, 4, and 5, if three bits B1, B2, and B3 are written in each memory cell MC, the memory cells MC may have eight possible logical states, that is, an erase state E and first to seventh program states P1 to P7 based on the three bits B1, B2, and B3. For example, when bits B1, B2, and B3 written in the memory cell MC are “111”, the memory cell MC may correspond to the erase state E and may be programmed to have a threshold voltage lower than a first voltage V1. When bits B1, B2, and B3 written in the memory cell MC are “011”, the memory cell MC may correspond to the first program state P1 and may be programmed to have a threshold voltage between the first voltage V1 and a second voltage V2. When bits B1, B2, and B3 written in the memory cell MC are “001”, the memory cell MC may correspond to the second program state P2 and may be programmed to have a threshold voltage between the second voltage V2 and a third voltage V3. When bits B1, B2, and B3 written in the memory cell MC are “000”, the memory cell MC may correspond to the third program state P3 and may be programmed to have a threshold voltage between the third voltage V3 and a fourth voltage V4. When bits B1, B2, and B3 written in the memory cell MC are “010”, the memory cell MC may correspond to the fourth program state P4 and may be programmed to have a threshold voltage between the fourth voltage V4 and a fifth voltage V5. When bits B1, B2, and B3 written in the memory cell MC are “110”, the memory cell MC may correspond to the fifth program state P5 and may be programmed to have a threshold voltage between the fifth voltage V5 and a sixth voltage V6. When bits B1, B2, and B3 written in the memory cell MC are “100”, the memory cell MC may correspond to the sixth program state P6 and may be programmed to have a threshold voltage between the sixth voltage V6 and a seventh voltage V7. When bits B1, B2, and B3 written in the memory cell MC are “101”, the memory cell MC may correspond to the seventh program state P7 and may be programmed to have a threshold voltage greater than the seventh voltage V7.

During a read operation, data written in the memory cells MC may be determined by distinguishing threshold voltages of memory cells MC using the first to seventh voltages V1 to V7.

The controller 120 may read bits B1, B2, and B3 written in the memory cell MC independently of each other. For example, during the read operation, the controller 120 may selectively read one of first data including first bits B1, second data including second bits B2, and third data including third bits B3 from memory cells selected as a read target.

As illustrated in FIG. 6, however, read counts corresponding to read operations of the first to third data may be different from each other. For example, upon reading of the first data including the first bits B1, a determination may be made as to whether the first bits B1 written in memory cells selected as a read target are “1” or “0”. As depicted in FIG. 6 by a bold line, the nonvolatile memory device 110 may read the first data through read operations using the first voltage V1 and the fifth voltage V5, that is, by performing the read operation twice. When reading the second data including the second bits B2, the nonvolatile memory device 110 may read the second data through read operations using the second voltage V2, the fourth voltage V4, and the sixth voltage V6, that is, by performing the read operation three times. When reading the third data including the third bits B3, the nonvolatile memory device 110 may read the third data through read operations using the third voltage V3 and the seventh voltage V7, that is, by performing the read operation twice.

As the number of times that a read operation is performed to read the first, second, or third data (or a total of time during which a non-selection read voltage is applied) increases, the quantity of read disturbance occurring during the read operation increases. Accordingly, in the case where read counts associated with read operations of the first to third data written in selected memory cells MC are different from each other, a read weight may be additionally adjusted according to whether any data is a read target.

In FIG. 6, logical states and bit values corresponding thereto are exemplary, and embodiments of the present disclosure may not be limited thereto.

FIG. 7 illustrates an example in which read weights are assigned according to distances between the substrate SUB and selected memory cells and a location of target data of pieces of data written in the selected memory cells. Referring to FIGS. 3, 4, and 7, first to seventh read weights W_1 to W_7 may be assigned to memory cells of the memory block BLKa. The first to seventh read weights W_1 to W_7 may have values that sequentially decrease. A value of the first read weight W_1 may have the greatest value, and the seventh read weight W_7 may have the smallest value.

As described with reference to FIG. 5, a read weight indicating the read disturbance may decrease as a distance between memory cells (selected as a read target) and the substrate SUB increases. For example, with regard to read operations of the first data including the first bits B1, a read weight may decrease in the order of the third, fifth, sixth, and seventh weights W_3, W_5, W_6, and W_7 as a distance between the selected memory cells and the substrate SUB increases. With regard to read operations of the second data including the second bits B2, a read weight may decrease in the order of the first, second, fourth, and sixth weights W_1, W_2, W_4, and W_6 as a distance between the selected memory cells and the substrate SUB increases. With regard to read operations of the third data including the third bits B3, a read weight may decrease in the order of the third, fifth, sixth, and seventh weights W_3, W_5, W_6, and W_7 as a distance between the selected memory cells and the substrate SUB increases.

As described with reference to FIG. 6, a read weight may increase as the number of times that a read operation is performed (i.e., to read the first, second, or third data) increases. For example, in memory cells belonging to the first word line group WLG1, the third read weight W_3 may be added to a read count upon reading of the first or third data accompanying two read operations, and the first read weight W_1 may be added to a read count upon reading of the second data accompanying three read operations. In memory cells belonging to the second word line group WLG2, the fifth read weight W_5 may be added to a read count upon reading of the first or third data accompanying two read operations, and the second read weight W_2 may be added to a read count upon reading of the second data accompanying three read operations. In memory cells belonging to the third word line group WLG3, the sixth read weight W_6 may be added to a read count upon reading of the first or third data accompanying two read operations, and the fourth read weight W_4 may be added to a read count upon reading of the second data accompanying three read operations. In memory cells belonging to the fourth word line group WLG4, the seventh read weight W_7 may be added to a read count upon reading of the first or third data accompanying two read operations, and the sixth read weight W_6 may be added to a read count upon reading of the second data accompanying three read operations.

As described above, the reliability and speed of the storage device 100 may be further improved by calculating a read weight in consideration of a location of data selected from pieces of data written in selected memory cells as well as a distance between the selected memory cells and the substrate SUB, that is, a location of the selected memory cells (or selected word lines). Notably, a location of data (e.g., within a memory cell) therefore has a different context and meaning than a location of a memory cell.

The number of read operations performed according to pieces of data (or locations of pieces of data) written in memory cells MC in a read operation is not limited to the exemplary numbers illustrated in FIGS. 6 and 7.

In an embodiment, information (i.e., or e.g., “read count information”) about the number of read operations to be performed for pieces of data (or locations of pieces of data) written in memory cells MC in a read operation (or read weights corresponding to the read count information) may be previously stored in the controller 120 as nonvolatile information upon manufacturing of the storage device 100. As another example, parameters for the read count information (or read weights corresponding to read count information) may be previously stored in the nonvolatile memory device 110 as nonvolatile information upon manufacturing of the storage device 100. When electric power is supplied to the storage device 100, the nonvolatile memory device 110 may provide the stored information to the controller 120.

FIG. 8 illustrates an example of read weights assigned additionally considering the string selection lines SSL1 to SSL4 of the memory block BLKa. Referring to FIGS. 3, 4, 7, and 8, first to ninth read weights W_1 to W_9 may be set according to memory cells selected as a read target. The first to ninth read weights W_1 to W_9 may have values that sequentially decrease.

When a read operation is performed on memory cells corresponding to the first string selection line SSL1, read weights may be set the same as that described with reference to FIG. 7.

When a read operation is performed on memory cells belonging to the first to third word line groups WLG1 to WLG3, read weights for memory cells corresponding to the first string selection line SSL1 are the same as read weights for memory cells corresponding to the second string selection line SSL2. However, when a read operation is performed on memory cells belonging to the fourth word line group WLG4, read weights for memory cells corresponding to the second string selection line SSL2 are smaller than read weights for memory cells corresponding to the first string selection line SSL1.

When a read operation is performed on memory cells belonging to the first to second word line groups WLG1 to WLG2, read weights for memory cells corresponding to the first string selection line SSL1 are the same as read weights for memory cells corresponding to the third or fourth string selection line SSL3 or SSL4. However, when a read operation is performed on memory cells belonging to the third and fourth word line groups WLG3 and WLG4, read weights for memory cells corresponding to the third or fourth string selection line SSL3 or SSL4 are smaller than read weights for memory cells corresponding to the first string selection line SSL1.

As described with reference to FIG. 8, if a read weight varies according to a string selection line (or a location of a string selection line) corresponding to selected memory cells, the reliability and speed of the storage device 100 may be further improved.

If the read disturbance occurs, charges may be discharged from charge trap layers of memory cells MC or may be trapped in the charge trap layers thereof. That is, charges move in the charge trap layers of the memory cells MC. If charges move, a stabilization time is needed until charges of the charge trap layers are stabilized. If a read operation is further performed before the stabilization time elapses after the read disturbance occurs at the memory cells MC, the read disturbance may occur additionally. If the read disturbance occurs additionally before charges trapped in the memory cells MC are stabilized, the influence of the read disturbance may increase more and more. Accordingly, an interval at which a read operation is performed (or the read disturbance occurs), in other words, the number of times that a read operation is performed may have an influence on a total of read disturbance, and this may be used to calculate the read weights.

FIG. 9 is a flowchart illustrating an example in which a read weight is adjusted according to the number of times that a read operation is performed. Referring to FIGS. 1, 3, and 9, in operation S210, the controller 120 determines whether a read operation is performed on the same memory block BLKa within a first predetermined critical time period Tcr1. For example, the controller 120 may determine whether a time interval between a read operation currently performed on the memory block BLKa and a read operation previously performed thereon is within the first predetermined critical time period Tcr1. If the time interval is greater than the first predetermined critical time period Tcr1 (S210=No), the read weight may not be adjusted additionally. If the time interval is within the first predetermined critical time period Tcr1 (S210=Yes), it may be determined that the second read disturbance occurs additionally due to a current read operation before charges of memory cells MC are stabilized after occurrence of the second read disturbance of a previous read operation in the memory block BLKa. Accordingly, in operation S220, a first iteration weight may be added to the read weight, and thus the read weight may increase.

In operation S230, the controller 120 determines whether a read operation is performed on the same word line within a second critical time period Tcr2. For example, the controller 120 may determine whether read operations currently performed and previously performed on the memory block BLKa are associated with the same word line of the memory block BLKa and a time interval between the read operations is within the second critical time period Tcr2. If the time interval is not less than the second critical time period Tcr2 (S230=No), the read weight may not be adjusted additionally. If the time interval is within the second critical time period Tcr2 (S230=Yes), it may be determined that the first read disturbance occurs additionally due to a current read operation before charges of memory cells MC are stabilized after occurrence of the first read disturbance of a previous read operation in the memory block BLKa. Accordingly, in operation S240, a second iteration weight may be added to the read weight, and thus the read weight may increase.

In an embodiment, the iteration weight may be subdivided for each section. For example, the controller 120 may count the number of times that the first iteration weight (or the second iteration weight) is continuously or sequentially added and may increase the first iteration weight (or the second iteration weight) as the count increases. Also, the controller 120 may reset the first iteration weight (or the second iteration weight) if the first iteration weight (or the second iteration weight) is not added during a predetermined time period in each memory block.

In an embodiment, the controller 120 may subdivide the first critical time period (or the second critical time period) into multiple sections. The controller 120 may variably select the first iteration weight (or the second iteration weight), based on whether a time interval between a previous read operation and a current read operation belongs to any section of the first critical time period (or the second critical time period). For example, the first iteration weight (or the second iteration weight) may increase as the time interval decreases.

The read disturbance may become greater as a temperature when a read operation is performed becomes lower, and as a difference between a temperature when a read operation is performed and a temperature when data is written in memory cells selected as a read target becomes greater. Accordingly, a read weight may be further adjusted by applying a temperature associated with a read operation.

FIG. 10 is a flowchart illustrating an example in which a read weight is adjusted based further on a temperature associated with a read operation. Referring to FIGS. 1, 3, and 10, in operation S310, the controller 120 determines whether a temperature TEMP when a read operation is performed is lower than a critical temperature TPcr. If the temperature TEMP is lower than the critical temperature TPcr (S310=Yes), in operation S320, the controller 120 may increase a read weight by adding a first temperature weight to the read weight. For example, the critical temperature TPcr may be −10 degrees Celsius.

In operation S330, the controller 120 determines whether a temperature difference TEMP_D between a temperature when a read operation is performed and a temperature when data is written in memory cells selected as a read target is higher than a critical temperature difference TDcr. If the temperature difference TEMP_D is higher than the critical temperature difference TDcr (S330=Yes), in operation S340, the controller 120 may increase the read weight by adding a second temperature weight to the read weight.

In an embodiment, as described with reference to FIG. 9, the first temperature weight or the second temperature weight may be subdivided according to sections of the critical temperature TPcr or the critical temperature difference TDcr.

As described above, the storage device 100 according to an embodiment of the present disclosure may estimate the practical read disturbance occurring in a read operation in consideration of memory cells selected for the read operation, data to be read, the number of times that the read operation is performed, and an environment (e.g., a temperature) parameter associated with the read operation. The storage device 100 may apply the estimation result to the read weight, and may increase a read count based on the read weight. The read count is used as a criterion for determining whether to perform a refresh operation. Accordingly, since the refresh operation is performed based on the practical read disturbance occurring when read operations are performed, the reliability and speed of the storage device 100 may be improved.

FIG. 11 is a block diagram illustrating the controller 120 according to an embodiment of the present disclosure. Referring to FIGS. 1 and 11, the controller 120 includes a bus 121, a processor 122, a RAM 123, an ECC block 124, a host interface 125, a buffer control circuit 126, and a memory interface 127.

The bus 121 may be configured to provide a channel among components of the controller 120.

The processor 122 may control overall operations of the controller 120 and may execute a logical operation. The processor 122 may communicate with an external host device through the host interface 125, may communicate with the nonvolatile memory device 110 through the memory interface 127, and may communicate with the RAM 130 through the buffer control circuit 126. The processor 122 may control the storage device 100 using the RAM 123 as a working memory, a cache memory, or a buffer memory.

At least one of the flash translation layer FTL, the weight module WM, and the counter CNT may be implemented in the form of software driven by the processor 122, such as firmware, an operating system, and an application. As another example, at least one of the flash translation layer FTL, the weight module WM, and the counter CNT may be implemented with hardware, such as circuitry or an integrated circuit, in the interior of the processor 122. Alternatively, at least one of the flash translation layer FTL, the weight module WM, and the counter CNT may be implemented in the form of a combination of hardware and software in connection with the processor 122. Alternatively, at least one of the flash translation layer FTL, the weight module WM, and the counter CNT may be implemented with a module that is separated from the processor 122.

The RAM 123 may be used as a working memory, a cache memory, or a buffer memory of the processor 122. The RAM 123 may store codes or commands that the processor 122 will execute. The RAM 123 may store data processed by the processor 122. The RAM 123 may include a static RAM (SRAM).

The ECC block 124 may perform an error correction operation. The ECC block 124 may perform error correction encoding based on data to be written in the nonvolatile memory device 110 through the memory interface 127. The error correction encoded data may be provided to the nonvolatile memory device 110 through the memory interface 127. The ECC block 124 may perform error correction decoding on data received through the memory interface 127 from the nonvolatile memory device 110. In an embodiment, the ECC block 124 may be included in the memory interface 127 as a component of the memory interface 127.

The host interface 125 may be configured to communicate with the external host device under control of the processor 122. The host interface 125 may convey communications using at least one of various communication manners, such as a universal serial bus (USB), a serial AT attachment (SATA), a serial attached SCSI (SAS), a high speed interchip (HSIC), a small computer system interface (SCSI), a peripheral component interconnection (PCI), a PCI express (PCIe), a nonvolatile memory express (NVMe), a universal flash storage (UFS), a secure digital (SD), a multimedia card (MMC), an embedded MMC (eMMC), a dual in-line memory module (DIMM), a registered DIMM (RDIMM), and a load reduced DIMM (LRDIMM).

The buffer control circuit 126 may control the RAM 123 under control of the processor 122.

The memory interface 127 may communicate with the nonvolatile memory device 110 in response to control of the processor 122. As described with reference to FIG. 1, the memory interface 127 may convey a command, an address, and data to the nonvolatile memory package 110 through the input/output channel. The memory interface 127 may convey a control signal to the nonvolatile memory device 110 through the control channel.

In an embodiment, in the case where the storage device 100 does not include the RAM 130, the controller 120 may not include the buffer control circuit 126.

In an embodiment, the processor 122 may control the controller 120 by using codes. The processor 122 may load codes from a nonvolatile memory device (e.g., a read only memory) that is implemented in the interior of the controller 120. Alternatively, the processor 122 may load codes from the nonvolatile memory device 110 through the memory interface 127.

In an embodiment, the bus 121 of the controller 120 may be divided into a control bus and a data bus. In an embodiment, the data bus may transfer data in the controller 120, and the control bus may transfer the following control information in the controller 120: a command and an address. The data bus and the control bus may be independent of each other to prevent mutual interference or influence. The data bus may be connected with the ECC block 124, the host interface 125, the buffer control circuit 126, and the memory interface 127. The control bus may be connected with the processor 122, the RAM 123, the host interface 125, the buffer control circuit 126, and the memory interface 127.

FIG. 12 is a block diagram illustrating a storage device 200, according to an embodiment of the present disclosure. Referring to FIG. 12, the storage device 200 includes a nonvolatile memory device 210, a controller 220, and a buffer memory 230.

The nonvolatile memory device 210 may perform a write operation, a read operation, and an erase operation under control of the controller 220. The nonvolatile memory device 210 may receive a write command, an address, and data from the controller 220 and may write the data in a storage space corresponding to the address. The nonvolatile memory device 210 may receive a read command and an address from the controller 220, may read data from a storage space corresponding to the address, and may output the read data to the controller 220. The nonvolatile memory device 210 may receive an erase command and an address from the controller 220 and may erase data of a storage space corresponding to the address.

The nonvolatile memory device 210 may include a plurality of memory blocks BLK1 to BLKz. Each of the memory blocks BLK1 to BLKz may include a plurality of memory cells. The memory cells may form a storage space of the nonvolatile memory device 210. Each of the memory blocks BLK1 to BLKz may further include selection transistors that allow memory cells to be selected independently of each other. The memory blocks BLK1 to BLKz may be distinguished according to an operational characteristic or a structural characteristic of the nonvolatile memory device 210. Since an example in which the memory blocks BLK1 to BLKz are distinguished from each other is described with reference to FIG. 3, a description thereof is thus omitted.

The nonvolatile memory device 210 may include a flash memory, a phase change random access memory (PRAM), a ferroelectric RAM (FeRAM), a magnetic RAM (MRAM), a resistive RAM (RRAM), etc.

The controller 220 may access the nonvolatile memory device 210 and the buffer memory 230. The controller 220 may control a write operation, a read operation, and an erase operation in response to a request of an external host device (not illustrated). The controller 220 may write write-requested data in the nonvolatile memory device 210. The controller 220 may read read-requested data from the nonvolatile memory device 210 and may output the read data to the external host device.

The controller 220 may manage the storage device 200 by using the buffer memory 230. For example, the controller 220 may temporarily store data to be written in the nonvolatile memory device 210 or data read from the nonvolatile memory device 210 in the buffer memory 230. The controller 220 may load metadata, which is needed to manage the nonvolatile memory device 210, on the buffer memory 230.

The controller 220 may receive a request, which is based on logical addresses, from the external host device. A flash translation layer (FTL) that is driven by the controller 220 may translate a logical address to a physical address of the nonvolatile memory device 210. The controller 220 may provide the physical address to the nonvolatile memory device 210. Mapping data MD that is needed for translation between a logical address and a physical address may be stored in the nonvolatile memory device 210 and may be loaded and used on the buffer memory 230. The flash translation layer FTL may perform translation between a logical address and a physical address based on the mapping data MD loaded on the buffer memory 230.

The controller 220 may include a reclaim module RM and a counter CNT. The controller 220 may count read operations performed in the nonvolatile memory device 210. For example, the controller 220 may manage a read count of each data group written in the nonvolatile memory device 210. The data group may indicate data of a preset size, and the size of the data group may be not more than the maximum data size writable in each memory block and is not less than the maximum data size writable in each page (the page has been described with reference to FIG. 3). The size of each data group may be determined to be a multiple of the maximum data size of each page.

When the reclaim module RM performs a read reclaim operation, the reclaim module RM may adjust a location of a new memory block, at which data groups are to be written, based on read counts of data groups in a memory block selected as a read reclaim target. For example, the read reclaim operation may include reading valid data of the selected memory block, writing the read valid data in the new memory block, and invalidating the valid data of the selected memory block. Whether data or a data group is valid or invalid may be managed by the flash translation layer FTL, and a validation or an invalidation result may be stored as the mapping data MD.

In an embodiment, each of the flash translation layer FTL, the reclaim module RM, and the counter CNT of the controller 220 may be implemented with a circuit, a state machine, software, firmware, or a combination of two or more thereof.

FIG. 13 is a flowchart illustrating an operating method of the storage device 200, according to another embodiment of the present disclosure. Referring to FIGS. 12 and 13, in operation S410, the controller 220 may count the number of read operations of each data group in each memory block. For example, the controller 220 may provide the nonvolatile memory device 210 with a read command for reading data belonging to each data group and may calculate the event that the nonvolatile memory device 210 completes a read operation in response to the read command, as one read count. The controller 220 may count read counts of each memory block as well as read counts of each data group. For example, the read counts may be stored in the buffer memory 230 or the nonvolatile memory device 210.

In operation S420, the controller 220 may determine whether to perform a read reclaim operation. For example, if a read count of each memory block reaches a preset threshold value, the controller 220 may determine that there is a need to perform the read reclaim operation on the corresponding memory block. If it is determined that there is no need to perform the read reclaim operation, the process proceeds to operation S410. If it is determined that there is a need to perform the read reclaim operation, the process proceeds to operation S430.

In operation S430, the controller 220 may detect read counts of valid data groups of a selected memory block. In operation S440, the controller 220 may relocate a location of at least one data group having a read count larger than the threshold value while performing the read reclaim operation. For example, after performing the read reclaim operation, the controller 220 may reset read counts of data groups.

As described above, the degrees of read disturbance that memory cells experience may differ from each other for respective locations of memory cells in each memory block. FIG. 14 shows an example in which the degrees of read disturbance differ from each other for respective locations of memory cells MCs. In FIG. 14, each memory cell is expressed by a cube. In FIG. 14, there are arranged memory cells MCs that are defined by first to eighth heights H1 to H8 corresponding to first to eighth word lines WL1 to WL8, first to fourth rows R1 to R4 corresponding to first to fourth string selection lines SSL1 to SSL4, and first to fourth columns C1 to C4 corresponding to first to fourth bit lines BL1 to BL4.

The memory cells MCs may be classified into first to fifth cell groups CG1 to CG5 based on the degree of read disturbance. The degree of read disturbance of the first cell group CG1 may be larger than the degree of read disturbance of the second cell group CG2. The degree of read disturbance of a k-th cell group may be larger than the degree of read disturbance of a (k+1)-th cell group.

Data written in the fifth cell group CG5 experience read disturbance that is less than that of data written in the first cell group CG1. If data of a high read frequency are written in the first cell group CG1 in which less read disturbance is generated and data of a low read frequency is written in the fifth cell group CG5 in which more read disturbance is generated, when read operations are performed, the total degree of read disturbance generated in the first cell group CG1 may be similar to the total degree of read disturbance generated in the fifth cell group CG5. Accordingly, it may be possible to improve the reliability of data written in the memory cells MCs and to reduce the numbers of read reclaim operations.

FIG. 15 shows an example in which data groups DG1 and DG2 of a selected memory block are written in a new (e.g., free) memory block during a read reclaim operation. In an embodiment, it is assumed that data written in memory cells MCs belonging to one height form one data group. However, embodiments of the present disclosure may not be limited thereto.

Referring to FIGS. 12 and 15, when the controller 220 performs the read reclaim operation, the controller 220 may detect read counts of the valid data groups DG1 and DG2. For example, a read count of the first data group DG1 may be larger than the threshold value, and a read count of the second data group DG2 may be smaller than the threshold value. The controller 220 may control read reclaim such that the first data group DG1 is written in memory cells MCs at the eight height H8 (refer to FIG. 14), in which read disturbance is the smallest.

An embodiment is illustrated in which a location of the second data group DG2 and a location of the first data group DG1 are exchanged during the read reclaim operation. However, embodiments of the present disclosure may not be limited thereto. The second data group DG2 may be written at any other location. For example, the second data group DG2 may be relocated according to a read count of the second data group DG2 or read counts of other data groups (not illustrated). For example, locations of data groups of a selected memory block may be relocated according to the order of read counts. For example, the read reclaim may be controlled, for example, such that a data group having the largest read count, for example, the first data group DG1 is written at a location having the smallest read disturbance and a data group having the smallest read count is written at a location having the most read disturbance.

FIG. 16 shows an example in which the controller 220 performs a read reclaim operation. In an embodiment, the controller 220 may perform a read reclaim operation based on multi-threading MT. The controller 220 may perform read reclaim by a preset data unit while other operations, which are not associated with the read reclaim, such as a read operation and an erase operation are performed between read reclaim operations. For a brief description, it is assumed that a data unit of the read reclaim corresponds to a data group. However, the data unit of the read reclaim may be larger or smaller than the data group.

Referring to FIGS. 12 and 16, in operation S510, the controller 220 may read a valid data group of a selected memory block. For example, the controller 220 may sequentially select and read a valid data group in the order of the first word line WL1 (refer to FIG. 3) to the eighth word line WL8 or in the order of the eighth word line WL8 to the first word line WL1.

In operation S515, the controller 220 detects a read count of the read data group. For example, the controller 220 may detect the read count by reading an area of the buffer memory 230 or the nonvolatile memory device 210, in which the read count is stored.

In operation S520, the controller 220 determines whether the read count of the read data group is larger than the threshold value. If the read count is larger than the threshold value, operation S535 is performed. If the read count is not larger than the threshold value, operation S525 is performed.

In operation S525, the controller 220 may perform a program operation for writing a data group, which has a read count smaller than the threshold value, in a new memory block. For example, the controller 220 may perform the program operation while sequentially selecting free memory cells in the order of the first word line WL1 to the eighth word line WL8 or in the order of the eighth word line WL8 to the first word line WL1.

In operation S530, the controller 220 may determine whether a delayed data group exists. For example, the delay data group may occur in a situation that will be described in operation S550. The delayed data group may be buffered in the buffer memory 230 or the controller 220 and may be a data group the read reclaim of which is delayed. If it is determined that the delayed data group does not exist, the process proceeds to operation S510. If it is determined that the delayed data group exists, the process proceeds to operation S535.

If the read count of the read data group is larger than the threshold value or if the delayed data group exists, the process proceeds to operation S535. In operation S535, the controller 220 determines whether a current program location of a new memory block, at which the program operation is to be performed, corresponds to a robust location. For example, the controller 220 may determine whether the current program location corresponds to the seventh height H7 or the eighth location H8 (refer to FIG. 14). For example, if the number of delayed data groups is smaller than the number of the most robust seventh and eighth heights H7 and H8, the controller 220 may determine whether the current program location corresponds to the most robust seventh and eighth heights H7 and H8. If the number of delayed data groups is larger than the number of the most robust seventh and eighth heights H7 and H8 and is smaller than the number of fifth to eighth heights H5 to H8 including next robust heights, the controller may determine whether the current program location corresponds to the fifth to eighth heights H5 to H8. That is, the controller 220 may adjust the number of robust locations based on the number of delayed data groups. If the current program location corresponds to a robust location, the process proceeds to operation S540. If the current program location does not correspond to a robust location, the process proceeds to operation S550.

In operation S540, the controller 220 may perform the program operation. For example, the controller 220 may perform the program operation for writing a data group, of which a read count is the largest, from among delayed data groups at the current program location. Afterwards, the process proceeds to operation S550.

If the current program location is not a robust location, in operation S545, the controller 220 may delay the program operation of the selected data group (the read data group or the delayed data group).

In operation S550, the controller 220 may determine whether the written data group is the last valid data group. If the last valid data group is written, the read reclaim operation ends. If the written data group is not the last valid data group, the process proceeds to operation S510.

In short, the controller 220 may perform the read reclaim operation based on the data unit of the read reclaim operation and may check a read count when a read operation is performed on each data unit. A data unit having a read count smaller than the threshold value or less is programmed according to a program location order of a new memory block. A program operation on a data unit having a read count larger than threshold value is delayed until a robust location is selected as a program target in the program location order of the new memory block.

FIG. 17 shows another example in which the controller 220 performs a read reclaim operation. Referring to FIGS. 12 and 17, in operation S610, the controller 220 may detect read counts of valid data groups of a memory block that is selected as a read reclaim target.

In operation S620, the controller 220 may select data groups having read counts that are larger than the threshold value.

In operation S630, locations for the selected data groups may be selected. For example, the robust seventh and eighth heights H7 and H8 (refer to FIG. 14) may be selected as locations for the selected data groups. The number of robust locations may be adjusted according to the number of selected data groups. For example, if the number of selected data groups is “4”, the sixth to eighth heights H6 to H8 may be selected as robust locations.

In operation S640, the controller 220 determines whether a program location of a new memory block corresponds to one of the selected locations. If the program location of the new memory block does not correspond to one of the selected locations, the controller 220 may read (in operation S650) a valid data group other than the selected data groups and may perform the program operation (in operation S670) on the data group read in operation S650. If the program location of the new memory block corresponds to one of the selected locations, the controller 220 may read a data group corresponding to the program location in operation S660 and may perform the program operation on the data group corresponding to the program location in operation S670.

In operation S680, the controller 220 may determine whether the written data group is the last valid data group. If the last valid data group is written, the read reclaim operation ends. If the written data group is not the last valid data group, the process proceeds to operation S640.

In short, the controller 220 may in advance detect data groups having read counts, which are larger than the threshold value, when starting the read reclaim operation and may allocate program locations of the detected data groups in advance.

In FIG. 17, an embodiment is described in which data groups having read counts larger than the threshold value are detected and program locations of the detected data groups are selected. However, operation S620 of FIG. 17 may be changed to align data groups based on read counts, and operation S630 may be changed to select program locations that are respectively allocated to the aligned data groups.

FIG. 18 shows an example in which data groups are set, according to an embodiment of the present disclosure. Referring to FIGS. 14 and 18, as a first example E1, data programmed into memory cells belonging to the same height may be selected as one data group. As a second example E2, data programmed into memory cells belonging to the same column may be selected as one data group. As a third example E3, data programmed into memory cells belonging to the same row may be selected as one data group. As a fourth example E4, data programmed into memory cells belonging to the same page may be selected as one data group. As a fifth example E5, data programmed into memory cells belonging to the same cell group may be selected as one data group.

FIG. 19 is a block diagram illustrating the controller 220, according to an embodiment of the present disclosure. Referring to FIGS. 12 and 19, the controller 220 includes a bus 221, a processor 222, a RAM 223, an ECC block 224, a host interface 225, a buffer control circuit 226, and a memory interface 227.

The bus 221 is configured to provide a channel between elements of the controller 220.

The processor 222 may control overall operations of the controller 220 and may execute a logical operation. The processor 222 may communicate with an external host device through the host interface 225, may communicate with the nonvolatile memory device 210 through the memory interface 227, and may communicate with the RAM 230 through the buffer control circuit 226. The processor 222 may control the storage device 200 by using the RAM 223 as a working memory, a cache memory, or a buffer memory.

At least one of the flash translation layer FTL, the reclaim module RM, and the counter CNT may be implemented in the form of software driven by the processor 222, such as firmware, an operating system, and an application. As another example, at least one of the flash translation layer FTL, the reclaim module RM, and the counter CNT may be implemented with hardware, such as circuitry or an intellectual property (IP), within the processor 222. As another example, at least one of the flash translation layer FTL, the reclaim module RM, and the counter CNT may be implemented in the form of a combination of hardware and software in connection with the processor 222. As another example, at least one of the flash translation layer FTL, the reclaim module RM, and the counter CNT may be implemented with a module that is separated from the processor 222.

The RAM 223 may be used as a working memory, a cache memory, or a buffer memory of the processor 222. The RAM 223 may store codes or commands that the processor 222 will execute. The RAM 223 may store data processed by the processor 222. The RAM 223 may include a static RAM (SRAM).

The ECC block 224 may perform error correction. The ECC block 224 may perform error correction encoding based on data to be written in the nonvolatile memory device 210 through the memory interface 227. The error correction encoded data may be provided to the nonvolatile memory device 210 through the memory interface 227. The ECC block 224 may perform error correction decoding on data received through the memory interface 227 from the nonvolatile memory device 210. In an embodiment, the ECC block 224 may be included in the memory interface 227 as an element of the memory interface 227.

The host interface 225 may communicate with the external host device under control of the processor 222. The host interface 225 may be configured to communicate by using at least one of various communication manners, such as a universal serial bus (USB), a serial AT attachment (SATA), a serial attached SCSI (SAS), a high speed interchip (HSIC), a small computer system interface (SCSI), a peripheral component interconnection (PCI), a PCI express (PCIe), a nonvolatile memory express (NVMe), a universal flash storage (UFS), a secure digital (SD), a multimedia card (MMC), an embedded MMC (eMMC), a dual in-line memory module (DIMM), a registered DIMM (RDIMM), and a load reduced DIMM (LRDIMM).

The buffer control circuit 226 is configured to control the RAM 230 under control of the processor 222.

The memory interface 227 is configured to communicate with the nonvolatile memory device 210 in response to control of the processor 222. As described with reference to FIG. 19, the memory interface 227 may convey a command, an address, and data to the nonvolatile memory package 210 through the input/output channel. The memory interface 227 may convey a control signal to the nonvolatile memory device 210 through the control channel.

In an embodiment, in the case where the storage device 200 does not include the RAM 230, the controller 220 may not include the buffer control circuit 226.

In an embodiment, the processor 222 may control the controller 220 by using codes. The processor 222 may load codes from a nonvolatile memory device (e.g., a read only memory) that is implemented in the controller 220. As another embodiment, the processor 222 may load codes from the nonvolatile memory device 210 through the memory interface 227.

In an embodiment, the bus 221 of the controller 220 may be classified into a control bus and a data bus. The data bus may be configured to transmit data within the controller 220, and the control bus may be configured to transmit control information, such as a command and an address, within the controller 220. The data bus and the control bus may be independent of each other to prevent mutual interference or influence. The data bus may be connected with the ECC code block 224, the host interface 225, the buffer control circuit 226, and the memory interface 227. The control bus may be connected with the processor 222, the RAM 223, the host interface 225, the buffer control circuit 226, and the memory interface 227.

According to various embodiments, data of a high read frequency are written in memory cells situated at a location that deteriorates less in a read operation. Accordingly, it may be possible to provide the storage device having an improved operating speed and an operating method thereof.

As is traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as units or modules or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware and/or software. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

While the present disclosure describes exemplary embodiments, it will be apparent to those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the concepts described herein. Therefore, it should be understood that the above embodiments are not limiting, but illustrative. 

What is claimed is:
 1. A storage device comprising: a nonvolatile memory device comprising a plurality of memory blocks, each of which comprises string selection transistors connected to a plurality of string selection lines, ground selection transistors connected to a plurality of ground selection lines, and memory cells connected to a plurality of word lines; and a controller configured to read valid data groups of a first memory block, among the memory blocks, and write the valid data groups in a second memory block, among the memory blocks, during a read reclaim operation, wherein the controller assigns first locations of the second memory block, at which the valid data groups are written, based on read counts of the valid data groups.
 2. The storage device of claim 1, wherein when a read operation is performed on a data group, among the valid data groups, the controller increases a read count of the data group.
 3. The storage device of claim 1, wherein the controller resets the read counts after the valid data groups are written in the second memory block.
 4. The storage device of claim 1, wherein when a read count of a data group, among the valid data groups, is larger than a threshold value, the controller relocates the valid data groups such that the data group is written at a location of the second memory block that is robust to a read disturbance generated during a read operation.
 5. The storage device of claim 1, wherein: the controller performs first program operations in an order that is determined according to locations of memory cells of each memory block, among the memory blocks, and the controller sequentially reads the valid data groups of the first memory block in a preset order and determines whether a read count of each of the valid data groups, which is read, is larger than a threshold value.
 6. The storage device of claim 5, wherein when the read count of a data group, among the valid data groups that are read, is not more than the threshold value, the controller programs the data group at a current program location of the second memory block.
 7. The storage device of claim 5, wherein: when the read count of a data group, among the valid data groups that are read, is larger the threshold value, the controller determines whether a current program location of the second memory block is a location robust to a read disturbance, and when the current program location of the second memory block is the location robust to the read disturbance, the controller programs the data group at the current program location.
 8. The storage device of claim 7, wherein when the current program location of the second memory block is not the location robust to the read disturbance, the controller delays a second program operation of the data group and reads a next data group, among valid data groups, of the first memory block.
 9. The storage device of claim 8, wherein when the current program location of the second memory block is the location robust to the read disturbance, the controller performs the second program operation on the data group.
 10. The storage device of claim 1, wherein: the controller performs program operations in an order that is determined according to locations of memory cells of each memory block, among the memory blocks, and the controller reads the read counts of the valid data groups of the first memory block and selects valid data groups having read counts larger than a threshold value, from among the read counts.
 11. The storage device of claim 10, wherein the controller selects second locations of the second memory block where the valid data groups having read counts larger than the threshold value are to be written.
 12. The storage device of claim 11, wherein when a current program location of the second memory block is not one of the second locations, the controller reads one valid data group among the valid data groups having read counts less than or equal to the threshold value and programs the one valid data group at the current program location.
 13. The storage device of claim 11, wherein when a current program location of the second memory block is one of the second locations, the controller reads one valid data group among the valid data groups having read counts greater than the threshold value and programs the one valid data group at the current program location.
 14. The storage device of claim 1, wherein each of the valid data groups comprises data that are written in memory cells connected in common to one word line, memory cells corresponding in common to one bit line, memory cells corresponding in common to a string selection line, memory cells corresponding in common to a string selection line and a word line, or memory cells grouped according to a degree of robustness to a read disturbance.
 15. An operating method of a storage device which comprises a nonvolatile memory device and a controller, the method comprising: counting a number of read operations for each of data groups written in a first memory block of the nonvolatile memory device; and copying the data groups written in the first memory block to a second memory block of the nonvolatile memory device during a read reclaim operation, wherein locations where the data groups are written within the second memory block are assigned, during the read reclaim operation, based on the number of read operations counted for each of the data groups.
 16. A storage device comprising: a nonvolatile memory device comprising a first memory block and a second memory block; and a controller that: attributes an amount of accumulated read disturbances to each of multiple valid-data groups stored within the first memory block, identifies a first valid-data group, among the valid-data groups, having an amount of accumulated read disturbances exceeding a predetermined value, identifies a second valid-data group, among the valid-data groups, having an amount of accumulated read disturbances that does not exceed the predetermined value, writes, during a read reclaim operation and in response to identifying the first valid-data group, the first valid-data group to a first memory location within the second memory block that has a first degree of susceptibility to a read disturbance, and writes, during the read reclaim operation and in response to identifying the second valid-data group, the second valid-data group to a second memory location within the second memory block that has a second degree of susceptibility to the read disturbance, wherein the second degree of susceptibility to the read disturbance is greater than the first degree of susceptibility to the read disturbance.
 17. The storage device of claim 16, wherein for each of the valid-data groups, all data of the valid-data group is programmed into memory cells of the nonvolatile memory device: 1) addressed by the same bit line, the same word line, or the same string selection line, 2) belonging to the same page of the first memory block, or 3) having a predetermined range of susceptibilities to the read disturbance.
 18. The storage device of claim 16, wherein the amount of accumulated read disturbances for the first valid-data group reflects: a number of read operations executed on memory cells of the nonvolatile memory device storing data of the first valid-data group, or a period between sequential read operations on the memory cells.
 19. The storage device of claim 16, wherein the amount of accumulated read disturbances for the first valid-data group reflects: a temperature, during a read operation, of memory cells of the nonvolatile memory device storing data of the first valid-data group, or a difference between a temperature of the memory cells when the data is stored therein and the temperature of the memory cells when the data is read by the read operation.
 20. The storage device of claim 16, wherein the amount of accumulated read disturbances for the first valid-data group reflects cross-sectional areas of memory cells of the nonvolatile memory device storing data of the first valid- 